-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8170720: VetoableListDecorator: Indexes to remove are not aggregated #1675
8170720: VetoableListDecorator: Indexes to remove are not aggregated #1675
Conversation
👋 Welcome back mstrauss! A progress list of the required criteria for merging this PR into |
@mstr2 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 17 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, fix is trivial and tests all work as intended
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I confirm that the added tests fail without and pass with the fix.
/integrate |
Going to push as commit a176574.
Your commit was automatically rebased without conflicts. |
VetoableListDecorator
does not correctly report removed indices. Instead of reporting ranges like[0, 3)
, it always reports a pairwise list of single removals like[0, 1, 1, 2, 2, 3)
.The reason is a off-by-one error, and the fix is simple.
/reviewers 2
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jfx.git pull/1675/head:pull/1675
$ git checkout pull/1675
Update a local copy of the PR:
$ git checkout pull/1675
$ git pull https://git.openjdk.org/jfx.git pull/1675/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1675
View PR using the GUI difftool:
$ git pr show -t 1675
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jfx/pull/1675.diff
Using Webrev
Link to Webrev Comment